Prune 154 stale tracked files under backups/#13
Merged
Conversation
backups/ is a runtime snapshot/bundle directory — its README documents it as local-only, and .gitignore already ignored backups/scripts/* and backups/launchers/*.bak. But 154 files committed before those rules were added stayed tracked: old mqlaunch .bak versions, perf snapshots, and nested backup-of-backup snapshots (backups/scripts/<ts>/backups/scripts/<ts>/...). Nothing reads from backups/ — every live reference either writes into it (all guarded by mkdir -p) or excludes it from scanning. Remove the tracked cruft (history preserves it) and tighten .gitignore to ignore everything under backups/ except the README. Write scripts recreate their subdirs at runtime. Drops ~59k lines and 2.0M from the tree; clears the 15 false-positive bash -n hits that all lived under backups/. Full selftest + install-smoke green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
repo-signal doctorscored macos-scripts strong across the board (health 100, docs 100, AI 100, release 85). The one drag:backups/was the largest directory by far — 154 tracked files, ~2.0M, including:mqlaunch-*.sh.bakversions andmqlaunch-v2/v3stable copiesbackups/scripts/<ts>/backups/scripts/<ts>/...These were committed before
.gitignorestarted ignoringbackups/scripts/*andbackups/launchers/*.bak— gitignore doesn't untrack already-tracked files, so they lingered.Safe to remove
Audited every live reference to
backups/: each one either writes into it (create-debug-bundle.sh,document-functions.sh --backup,workspace.sh— all guarded bymkdir -p) or excludes it from scanning (lint.sh,install-smoke.sh, the menu finds). Nothing reads from it.Change
git rm -r backups/(history preserves everything).backups/README.mdso the documented runtime dir survives; subdirs are recreated on demand by the write scripts..gitignoretobackups/*+!backups/README.md.Result
Drops ~59k lines and 2.0M from the tree, and clears the 15 false-positive
bash -nhits that all lived underbackups/. Full selftest + install-smoke green; shell lint unchanged at 108 files (it already excluded backups).🤖 Generated with Claude Code